-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: mark window online test slow #41971
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
cc @mroeschke |
@stuartarchibald any pointers on how I could speed up our numba tests? Generally I have a parameterized test like this: pandas/pandas/tests/window/test_online.py Line 28 in 8c6e865
Where I am parameterizing over A typical numba function that is being jitted under the hood is like this: pandas/pandas/core/window/online.py Line 37 in 8c6e865
The size of the data in the tests is fairly small, but jitting a new version of these functions for each parameter combination seems to take quite a bit of time. |
@mroeschke prob ok to just have a couple of predefined numba options rather than doing them all (as not testing numba per se here) |
@mroeschke @jreback I agree, I think cutting down the options is probably a good idea. Numba's test suite is massive and independently tests these features (and permutations of) so it's probably best in view of runtime to focus on testing the things that are important to these Pandas features.
If you agree with the above, I think it would cut the test space down to |
if there isn't a better fix on the horizon i think marking as slow is reasonable. This test accounts for about a quarter of the runtime with --skip-slow locally |
Thanks for the insight @stuartarchibald. I'll make those changes in a follow up PR. As for this PR, I think marking as slow is still a good idea as @jbrockmendel mentioned |
thanks @mzeitlin11 @mroeschke ok to PR the limiting of the numba combinations as @stuartarchibald |
Co-authored-by: Matthew Zeitlin <[email protected]>
Seems like the new online tests added increase test runtime a lot, making failures like https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=61437&view=logs&j=404760ec-14d3-5d48-e580-13034792878f&t=f81e4cc8-d61a-5fb8-36be-36768e5c561a and
https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=61437&view=logs&j=404760ec-14d3-5d48-e580-13034792878f&t=f81e4cc8-d61a-5fb8-36be-36768e5c561a
more common. Slowest durations showing this are below, have marked these as slow as a potential solution